Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b14ce192de6b7473bed140df0672f8c62529cc3187a06ce5988c027eadc1b3f

Tx prefix hash: 989f07204717b3184692fd86b3eaf56f3082a69e3d48d58282727d2be79d3e1f
Tx public key: a153939042d9fca10e848809c58b6f4105ee4c6d116678252b1c1386b35aa25d
Timestamp: 1736927309 Timestamp [UCT]: 2025-01-15 07:48:29 Age [y:d:h:m:s]: 00:155:10:07:44
Block: 1197742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110779 RingCT/type: yes/0
Extra: 01a153939042d9fca10e848809c58b6f4105ee4c6d116678252b1c1386b35aa25d021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 696889a35816cc435f0d5b973e3e3574c69023aa9b01e142ba7c1219157fe709 0.600000000000 1684357 of 15

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": 1197752, "vin": [ { "gen": { "height": 1197742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "696889a35816cc435f0d5b973e3e3574c69023aa9b01e142ba7c1219157fe709" } } ], "extra": [ 1, 161, 83, 147, 144, 66, 217, 252, 161, 14, 132, 136, 9, 197, 139, 111, 65, 5, 238, 76, 109, 17, 102, 120, 37, 43, 28, 19, 134, 179, 90, 162, 93, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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