Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 439861fde31e4d9c980ba0ea92e7084f558fba8eea9215c0421e82d88a20ed8d

Tx prefix hash: 9013d71becc9f94201340a6fd1866fda07224eecf3319fe44e3aa5b349aaa4f5
Tx public key: 0f4443eef785f9b13b24628a13152d7a6cca40b0557d2a45cbff8adbabc7f924
Timestamp: 1716772179 Timestamp [UCT]: 2024-05-27 01:09:39 Age [y:d:h:m:s]: 00:354:22:12:32
Block: 1030804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253680 RingCT/type: yes/0
Extra: 010f4443eef785f9b13b24628a13152d7a6cca40b0557d2a45cbff8adbabc7f924021100000005e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27516400fc220f7a2cbf5966e3eeeff607aca16e4a2f4e741b26c095bafe7032 0.600000000000 1499097 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": 1030814, "vin": [ { "gen": { "height": 1030804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27516400fc220f7a2cbf5966e3eeeff607aca16e4a2f4e741b26c095bafe7032" } } ], "extra": [ 1, 15, 68, 67, 238, 247, 133, 249, 177, 59, 36, 98, 138, 19, 21, 45, 122, 108, 202, 64, 176, 85, 125, 42, 69, 203, 255, 138, 219, 171, 199, 249, 36, 2, 17, 0, 0, 0, 5, 224, 133, 50, 182, 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