Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4cc791b3c51108a84710fa4d38f976a577889d61f5b3da4d84619c51708054b9

Tx prefix hash: 08a006eee7293d71aa4eafc792f2559c5c81f36767a72a1c22e49ff0fdeb327d
Tx public key: a2aea12d69dc5eb3c9df69d3fb596cb8ee79108ce87a929ab443c32b5a691340
Timestamp: 1634301819 Timestamp [UCT]: 2021-10-15 12:43:39 Age [y:d:h:m:s]: 03:024:05:51:12
Block: 353565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 795144 RingCT/type: yes/0
Extra: 01a2aea12d69dc5eb3c9df69d3fb596cb8ee79108ce87a929ab443c32b5a69134002110000002c5d7cc334000000000000000000

1 output(s) for total of 41.351646024000 dcy

stealth address amount amount idx
00: ddccc892850a3df66ee19db48325eb390a3a1931f4f58673747909c91d8c1459 41.351646024000 722455 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": 353575, "vin": [ { "gen": { "height": 353565 } } ], "vout": [ { "amount": 41351646024, "target": { "key": "ddccc892850a3df66ee19db48325eb390a3a1931f4f58673747909c91d8c1459" } } ], "extra": [ 1, 162, 174, 161, 45, 105, 220, 94, 179, 201, 223, 105, 211, 251, 89, 108, 184, 238, 121, 16, 140, 232, 122, 146, 154, 180, 67, 195, 43, 90, 105, 19, 64, 2, 17, 0, 0, 0, 44, 93, 124, 195, 52, 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