Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 78c6b140425e39a0261bb142b9246948f2bea4fe1d2d2067affd89aaced97712

Tx prefix hash: 48f0622c46428fb0e1dc1f4d0de7dde2d1a0fc5996e0b6b267f6fec14c953317
Tx public key: f0f3515d494a8b74f65ddaa97deb009ac25755e341357c553f10fbfd20178af0
Timestamp: 1696915332 Timestamp [UCT]: 2023-10-10 05:22:12 Age [y:d:h:m:s]: 01:215:13:00:38
Block: 866379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 415100 RingCT/type: yes/0
Extra: 01f0f3515d494a8b74f65ddaa97deb009ac25755e341357c553f10fbfd20178af0021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.826659678000 dcy

stealth address amount amount idx
00: 538dccfcbc11c0152ea5d3288d8863028db581ad982b035b037e6a5ba3cc5c7a 0.826659678000 1320969 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 866389, "vin": [ { "gen": { "height": 866379 } } ], "vout": [ { "amount": 826659678, "target": { "key": "538dccfcbc11c0152ea5d3288d8863028db581ad982b035b037e6a5ba3cc5c7a" } } ], "extra": [ 1, 240, 243, 81, 93, 73, 74, 139, 116, 246, 93, 218, 169, 125, 235, 0, 154, 194, 87, 85, 227, 65, 53, 124, 85, 63, 16, 251, 253, 32, 23, 138, 240, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8