Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c70c45077106acee41d9169368ad7a38ed5d1c83f36783a5d25915b950336c6

Tx prefix hash: fa6918610413fad4ffcf80609031fbe46e4990de9d492ca999366586b057fbc7
Tx public key: 327766e81112b3db73dc708e4adac626834e010b2eea2de40719253e3dfb4b43
Timestamp: 1710584567 Timestamp [UCT]: 2024-03-16 10:22:47 Age [y:d:h:m:s]: 00:304:16:49:33
Block: 979514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218091 RingCT/type: yes/0
Extra: 01327766e81112b3db73dc708e4adac626834e010b2eea2de40719253e3dfb4b430211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4aa18a18db9a97b2f7df40ab93073ec5eb7bf5f9cdc1ec7f591c2c5b66b7dc27 0.600000000000 1439549 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": 979524, "vin": [ { "gen": { "height": 979514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4aa18a18db9a97b2f7df40ab93073ec5eb7bf5f9cdc1ec7f591c2c5b66b7dc27" } } ], "extra": [ 1, 50, 119, 102, 232, 17, 18, 179, 219, 115, 220, 112, 142, 74, 218, 198, 38, 131, 78, 1, 11, 46, 234, 45, 228, 7, 25, 37, 62, 61, 251, 75, 67, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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