Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46161dd2edfd11855d7fd61828430ed327b5631b6f4604bc9cf6ba7f1e0988af

Tx prefix hash: bf115be781d7cc8ca575b896787bf1ee4d8fc02a4544ec6b23b7a00167886760
Tx public key: 4e73ab13d7c2b9db75fbd1c9865642e162f9467bc0b1a540863989cb3ffd32d1
Timestamp: 1728628639 Timestamp [UCT]: 2024-10-11 06:37:19 Age [y:d:h:m:s]: 00:129:16:35:12
Block: 1129094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92422 RingCT/type: yes/0
Extra: 014e73ab13d7c2b9db75fbd1c9865642e162f9467bc0b1a540863989cb3ffd32d1021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1bb7ce02f555c1b2a62669497e16d12bdf864cd601b130eaa4de3f29730ead5d 0.600000000000 1611917 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": 1129104, "vin": [ { "gen": { "height": 1129094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1bb7ce02f555c1b2a62669497e16d12bdf864cd601b130eaa4de3f29730ead5d" } } ], "extra": [ 1, 78, 115, 171, 19, 215, 194, 185, 219, 117, 251, 209, 201, 134, 86, 66, 225, 98, 249, 70, 123, 192, 177, 165, 64, 134, 57, 137, 203, 63, 253, 50, 209, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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