Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcb0a147e0396fd7aaae3117c240f94e2397f6e99b157305b3657e7bf7c1f8d7

Tx prefix hash: 3ee996aeaa3cc7bc59a38bc9b9b0510d7c38f495626a820fdd4313778800b090
Tx public key: 79d2682167fc04248f9b148355df2d3f5416f60a308a62dad0f251ea5896dbb0
Timestamp: 1724703061 Timestamp [UCT]: 2024-08-26 20:11:01 Age [y:d:h:m:s]: 00:137:00:52:12
Block: 1096530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98038 RingCT/type: yes/0
Extra: 0179d2682167fc04248f9b148355df2d3f5416f60a308a62dad0f251ea5896dbb0021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e38aef9a6674dc9ac6463d5988587df476087fa71e805dc22c9706d9b560064d 0.600000000000 1571721 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": 1096540, "vin": [ { "gen": { "height": 1096530 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e38aef9a6674dc9ac6463d5988587df476087fa71e805dc22c9706d9b560064d" } } ], "extra": [ 1, 121, 210, 104, 33, 103, 252, 4, 36, 143, 155, 20, 131, 85, 223, 45, 63, 84, 22, 246, 10, 48, 138, 98, 218, 208, 242, 81, 234, 88, 150, 219, 176, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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