Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dcc705fd8bffe8a15f4b0d49a4ec2974aa1fd08109cd02b5ddc94de0345251c1

Tx prefix hash: b2f7bbff40f783a152d69b407e0d742cfa3eceb9113bcb286262cb02124eaa5b
Tx public key: 08f9033a2f1ca66ae63ebb9a8091437b5544cfc06b18d4868f2b28c4b7e75edf
Timestamp: 1670077836 Timestamp [UCT]: 2022-12-03 14:30:36 Age [y:d:h:m:s]: 02:181:00:18:07
Block: 644574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 651123 RingCT/type: yes/0
Extra: 0108f9033a2f1ca66ae63ebb9a8091437b5544cfc06b18d4868f2b28c4b7e75edf021100000003272bcc39000000000000000000

1 output(s) for total of 4.490128367000 dcy

stealth address amount amount idx
00: 0f7bd22d758ef1fbd59098ae04949568ddd3af590d788f5b76c105189be7fabb 4.490128367000 1084631 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": 644584, "vin": [ { "gen": { "height": 644574 } } ], "vout": [ { "amount": 4490128367, "target": { "key": "0f7bd22d758ef1fbd59098ae04949568ddd3af590d788f5b76c105189be7fabb" } } ], "extra": [ 1, 8, 249, 3, 58, 47, 28, 166, 106, 230, 62, 187, 154, 128, 145, 67, 123, 85, 68, 207, 192, 107, 24, 212, 134, 143, 43, 40, 196, 183, 231, 94, 223, 2, 17, 0, 0, 0, 3, 39, 43, 204, 57, 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