Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0354e6e58684c00783388195647b3cbcd8bccedb21937a22e2bc88517640c76

Tx prefix hash: 3ea8ecab0049b7e41dc0894c23a0c775c5606a4fb0381c7c2e183ac5d229bdb7
Tx public key: 4f758fb3a9f0582cefa038092972d9a39071c973a92d1d395bfc4229acc98e8a
Timestamp: 1714497144 Timestamp [UCT]: 2024-04-30 17:12:24 Age [y:d:h:m:s]: 00:322:18:29:53
Block: 1011936 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230740 RingCT/type: yes/0
Extra: 014f758fb3a9f0582cefa038092972d9a39071c973a92d1d395bfc4229acc98e8a0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1b8b5ec3a691e7996d6b29b77833eb5a6979debbeb63a33366a59f6c827e418 0.600000000000 1474302 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": 1011946, "vin": [ { "gen": { "height": 1011936 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1b8b5ec3a691e7996d6b29b77833eb5a6979debbeb63a33366a59f6c827e418" } } ], "extra": [ 1, 79, 117, 143, 179, 169, 240, 88, 44, 239, 160, 56, 9, 41, 114, 217, 163, 144, 113, 201, 115, 169, 45, 29, 57, 91, 252, 66, 41, 172, 201, 142, 138, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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