Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e227ffd9344180da34e2b648c9328ad5ceb41ffc187c10a962ccef0956c2461d

Tx prefix hash: 972f3ee24ca75f6a867e2a5130fab80af315c1007a4febfcf6d04b0e671ec940
Tx public key: 9e9d4124e6e3d7ac8f0ba98427fba6de56e3b1ec5f8c4d552def0e33439e2e02
Timestamp: 1673196125 Timestamp [UCT]: 2023-01-08 16:42:05 Age [y:d:h:m:s]: 02:099:12:56:14
Block: 670381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 592829 RingCT/type: yes/0
Extra: 019e9d4124e6e3d7ac8f0ba98427fba6de56e3b1ec5f8c4d552def0e33439e2e0202110000000552542ceb000000000000000000

1 output(s) for total of 3.687647626000 dcy

stealth address amount amount idx
00: b7d42ecb3aeff5a228b2ddea4cb30b8c712d269b78d99ee3702e650accc6c2ac 3.687647626000 1111782 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": 670391, "vin": [ { "gen": { "height": 670381 } } ], "vout": [ { "amount": 3687647626, "target": { "key": "b7d42ecb3aeff5a228b2ddea4cb30b8c712d269b78d99ee3702e650accc6c2ac" } } ], "extra": [ 1, 158, 157, 65, 36, 230, 227, 215, 172, 143, 11, 169, 132, 39, 251, 166, 222, 86, 227, 177, 236, 95, 140, 77, 85, 45, 239, 14, 51, 67, 158, 46, 2, 2, 17, 0, 0, 0, 5, 82, 84, 44, 235, 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