Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7f5ebed5350b189a8bc348b68d69cb3a83562b247babe3c587c082a728f444e0

Tx prefix hash: 8e0e81cfc47baeaf57fb514ea62542e75f52f56d31e4434d58ef762370cba369
Tx public key: 418ca56e34697008f41623c6b06ec34b30ccd2ee08ad1344f5c1298ea1b5e36d
Timestamp: 1697334881 Timestamp [UCT]: 2023-10-15 01:54:41 Age [y:d:h:m:s]: 01:178:08:57:53
Block: 869849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 388519 RingCT/type: yes/0
Extra: 01418ca56e34697008f41623c6b06ec34b30ccd2ee08ad1344f5c1298ea1b5e36d02110000000133af99f4000000000000000000

1 output(s) for total of 0.805061761000 dcy

stealth address amount amount idx
00: b271c7886c8f4c21341e69be616acf256779eafaf72cc7068c7a3067b793d90a 0.805061761000 1324712 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": 869859, "vin": [ { "gen": { "height": 869849 } } ], "vout": [ { "amount": 805061761, "target": { "key": "b271c7886c8f4c21341e69be616acf256779eafaf72cc7068c7a3067b793d90a" } } ], "extra": [ 1, 65, 140, 165, 110, 52, 105, 112, 8, 244, 22, 35, 198, 176, 110, 195, 75, 48, 204, 210, 238, 8, 173, 19, 68, 245, 193, 41, 142, 161, 181, 227, 109, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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