Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72d80279e67be030df4c8a94ab2ea0865a8cf38570c76b44b3a2efac40fe948a

Tx prefix hash: c57e845e7d8d1633112375bf17fa044baa03e3919ecdfe019baa58d84412fcea
Tx public key: ba42134322e8c60a0e7217044df4896c5d53d446f629c5dbde3e59aa4851609d
Timestamp: 1695336935 Timestamp [UCT]: 2023-09-21 22:55:35 Age [y:d:h:m:s]: 01:248:20:07:23
Block: 853276 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438955 RingCT/type: yes/0
Extra: 01ba42134322e8c60a0e7217044df4896c5d53d446f629c5dbde3e59aa4851609d02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.913571309000 dcy

stealth address amount amount idx
00: 8924df70fcdc93ec0b337a31065a151d8142d191ffe9dfd12b92b9779a42c294 0.913571309000 1307176 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": 853286, "vin": [ { "gen": { "height": 853276 } } ], "vout": [ { "amount": 913571309, "target": { "key": "8924df70fcdc93ec0b337a31065a151d8142d191ffe9dfd12b92b9779a42c294" } } ], "extra": [ 1, 186, 66, 19, 67, 34, 232, 198, 10, 14, 114, 23, 4, 77, 244, 137, 108, 93, 83, 212, 70, 246, 41, 197, 219, 222, 62, 89, 170, 72, 81, 96, 157, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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