Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 137e373c2cfb09dbe4e59f34c1c5dfdaf33c881e2fddaecf845b3b3bb1ec51bb

Tx prefix hash: fe016fad0a1be17f3a550117f0b783a89e1890f94e4d893489ae19f8b321b223
Tx public key: 61f801bf8411c87daf5f4269d7763e7c9219c8b0db2ad09eea8dcce8f8a9380f
Timestamp: 1639606862 Timestamp [UCT]: 2021-12-15 22:21:02 Age [y:d:h:m:s]: 03:134:03:23:17
Block: 396334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 874641 RingCT/type: yes/0
Extra: 0161f801bf8411c87daf5f4269d7763e7c9219c8b0db2ad09eea8dcce8f8a9380f021100000001eaa12622000000000000000000

1 output(s) for total of 29.838795548000 dcy

stealth address amount amount idx
00: 342efc4b9c54256edca7e58a49d384616abf9f9d21f6a7b3d4e2ec0d79f7a9aa 29.838795548000 794588 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": 396344, "vin": [ { "gen": { "height": 396334 } } ], "vout": [ { "amount": 29838795548, "target": { "key": "342efc4b9c54256edca7e58a49d384616abf9f9d21f6a7b3d4e2ec0d79f7a9aa" } } ], "extra": [ 1, 97, 248, 1, 191, 132, 17, 200, 125, 175, 95, 66, 105, 215, 118, 62, 124, 146, 25, 200, 176, 219, 42, 208, 158, 234, 141, 204, 232, 248, 169, 56, 15, 2, 17, 0, 0, 0, 1, 234, 161, 38, 34, 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