Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1dee923e44fbaaa22f2928ec75923cae8a8a57570aa3c848f4f1e522351066d

Tx prefix hash: f7eb4ca2efc106e95bd07e879785ca126d92b46ccbbc65ac21a1abf8ad08b706
Tx public key: 88de6ba074d964db9834c820f9dbd79e64690d3276a0c76923838371c6108244
Timestamp: 1723721299 Timestamp [UCT]: 2024-08-15 11:28:19 Age [y:d:h:m:s]: 01:109:04:58:55
Block: 1088409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 336546 RingCT/type: yes/0
Extra: 0188de6ba074d964db9834c820f9dbd79e64690d3276a0c76923838371c6108244021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0618905d3037e1e14af2b473fb224ff7e818dc95c69e031234e89ec5d733c7a7 0.600000000000 1563024 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": 1088419, "vin": [ { "gen": { "height": 1088409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0618905d3037e1e14af2b473fb224ff7e818dc95c69e031234e89ec5d733c7a7" } } ], "extra": [ 1, 136, 222, 107, 160, 116, 217, 100, 219, 152, 52, 200, 32, 249, 219, 215, 158, 100, 105, 13, 50, 118, 160, 199, 105, 35, 131, 131, 113, 198, 16, 130, 68, 2, 17, 0, 0, 0, 5, 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