Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91e1bd6ae6d2a46da073e12df4fe9ec18fa05951c12c1200f205ddc6f4dda19a

Tx prefix hash: 8861947f64f2de7194736d82fb6c7f32fa032ca5d92708063e37ded867fa6fb1
Tx public key: 5b0c512ae86dc94d9f7216944c2b45ad3210641ee1b4c2600b1763722fe9b091
Timestamp: 1661680949 Timestamp [UCT]: 2022-08-28 10:02:29 Age [y:d:h:m:s]: 03:072:03:40:12
Block: 575574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 831391 RingCT/type: yes/0
Extra: 015b0c512ae86dc94d9f7216944c2b45ad3210641ee1b4c2600b1763722fe9b0910211000000016570b1ef000000000000000000

1 output(s) for total of 7.601240973000 dcy

stealth address amount amount idx
00: 739a322454e7ece4775decc1f896d1783e7ffb4d502434ff98e08d61277842d2 7.601240973000 1008912 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": 575584, "vin": [ { "gen": { "height": 575574 } } ], "vout": [ { "amount": 7601240973, "target": { "key": "739a322454e7ece4775decc1f896d1783e7ffb4d502434ff98e08d61277842d2" } } ], "extra": [ 1, 91, 12, 81, 42, 232, 109, 201, 77, 159, 114, 22, 148, 76, 43, 69, 173, 50, 16, 100, 30, 225, 180, 194, 96, 11, 23, 99, 114, 47, 233, 176, 145, 2, 17, 0, 0, 0, 1, 101, 112, 177, 239, 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