Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1136ae62cee440b265308772b9aa91905a0428cceaabec521eb2d4fdb3baf648

Tx prefix hash: 07e286a8bb560f7a2fa87963d957263aa2b462887f6e9e644a67496dafd9a448
Tx public key: f6d9d870691b2dd454cfe4651c9671a08ae3b7cee3b3b1da00036a6c2816020e
Timestamp: 1702361845 Timestamp [UCT]: 2023-12-12 06:17:25 Age [y:d:h:m:s]: 01:051:02:07:05
Block: 911330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297609 RingCT/type: yes/0
Extra: 01f6d9d870691b2dd454cfe4651c9671a08ae3b7cee3b3b1da00036a6c2816020e021100000008faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: abf9713bf5d34627ccf2bdaaf3f47ff7da7944181cf7f6a9192735ca01ab7534 0.600000000000 1368513 of 15

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": 911340, "vin": [ { "gen": { "height": 911330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "abf9713bf5d34627ccf2bdaaf3f47ff7da7944181cf7f6a9192735ca01ab7534" } } ], "extra": [ 1, 246, 217, 216, 112, 105, 27, 45, 212, 84, 207, 228, 101, 28, 150, 113, 160, 138, 227, 183, 206, 227, 179, 177, 218, 0, 3, 106, 108, 40, 22, 2, 14, 2, 17, 0, 0, 0, 8, 250, 243, 92, 156, 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