Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb916f9b803792bb845334229b5444ce8a8934d8977af76aa20e654d98391db4

Tx prefix hash: daf1b2c8fc238d9023fa6e6939d5998a87adaab9880ac74f0c5704a29d9fda3b
Tx public key: 79fe2f83660fd266a1acb1b1742d8386b60b1706ce472a4c0e2d2ede8d8532e2
Timestamp: 1738303130 Timestamp [UCT]: 2025-01-31 05:58:50 Age [y:d:h:m:s]: 00:040:21:13:46
Block: 1208879 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29249 RingCT/type: yes/0
Extra: 0179fe2f83660fd266a1acb1b1742d8386b60b1706ce472a4c0e2d2ede8d8532e20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bf11efb2d5b95fddda08b506e9fb4553f155b0555891ab4639370bee4429cea6 0.600000000000 1695614 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": 1208889, "vin": [ { "gen": { "height": 1208879 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bf11efb2d5b95fddda08b506e9fb4553f155b0555891ab4639370bee4429cea6" } } ], "extra": [ 1, 121, 254, 47, 131, 102, 15, 210, 102, 161, 172, 177, 177, 116, 45, 131, 134, 182, 11, 23, 6, 206, 71, 42, 76, 14, 45, 46, 222, 141, 133, 50, 226, 2, 17, 0, 0, 0, 5, 31, 10, 83, 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