Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5dd5905b5cc0f94ed58040bb144c503534a61ff872be9bc893774887c0f1bc4d

Tx prefix hash: fcda04d3f1eab5e52cdf770f3292d30009ae3c6660fda10b3fa718ab98f8470c
Tx public key: 0139ea0c657e02b6038ba6268a41b2cd2b93a6eec2b2d642059a5cc1a8014f10
Timestamp: 1706766547 Timestamp [UCT]: 2024-02-01 05:49:07 Age [y:d:h:m:s]: 01:138:01:47:03
Block: 947821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359683 RingCT/type: yes/0
Extra: 010139ea0c657e02b6038ba6268a41b2cd2b93a6eec2b2d642059a5cc1a8014f1002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3aa160bdec0bd78fda727d42cc1f388dec283051d9766b85f7bb390735541bd 0.600000000000 1406179 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": 947831, "vin": [ { "gen": { "height": 947821 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3aa160bdec0bd78fda727d42cc1f388dec283051d9766b85f7bb390735541bd" } } ], "extra": [ 1, 1, 57, 234, 12, 101, 126, 2, 182, 3, 139, 166, 38, 138, 65, 178, 205, 43, 147, 166, 238, 194, 178, 214, 66, 5, 154, 92, 193, 168, 1, 79, 16, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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