Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e15a80a39c8b2586136984fb28d2f1efbb05cb540a91b394c250535e9fe95d

Tx prefix hash: 834c10ba40017d44ea9e3039b654f5769e4c6920ba00a85d6e60fd2349534174
Tx public key: 6429244920bb4e207f4f01ff92a6ed81f0f33c9ee6d6fd755bc001712dc0ed4a
Timestamp: 1663218583 Timestamp [UCT]: 2022-09-15 05:09:43 Age [y:d:h:m:s]: 02:102:13:57:48
Block: 588260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594813 RingCT/type: yes/0
Extra: 016429244920bb4e207f4f01ff92a6ed81f0f33c9ee6d6fd755bc001712dc0ed4a02110000000c143619d6000000000000000000

1 output(s) for total of 6.900022356000 dcy

stealth address amount amount idx
00: 04acdbf740a9b7623ca5dab09aee2990352022caeeb923ada5602e16cde85e64 6.900022356000 1022461 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": 588270, "vin": [ { "gen": { "height": 588260 } } ], "vout": [ { "amount": 6900022356, "target": { "key": "04acdbf740a9b7623ca5dab09aee2990352022caeeb923ada5602e16cde85e64" } } ], "extra": [ 1, 100, 41, 36, 73, 32, 187, 78, 32, 127, 79, 1, 255, 146, 166, 237, 129, 240, 243, 60, 158, 230, 214, 253, 117, 91, 192, 1, 113, 45, 192, 237, 74, 2, 17, 0, 0, 0, 12, 20, 54, 25, 214, 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