Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cdc860b3421b5e46ef334bbb936c9c2b9f9b272764979281b71fba3738de070

Tx prefix hash: 002040f20b0fb2dc77ee57c5ad2781add6e35904f9686c3c3c6bf5456ed616dd
Tx public key: 511ca0a4c15a432c98668a7f5d94c730ae0067c199057baff0bba16f23101b3a
Timestamp: 1709760445 Timestamp [UCT]: 2024-03-06 21:27:25 Age [y:d:h:m:s]: 01:273:06:58:59
Block: 972680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 454071 RingCT/type: yes/0
Extra: 01511ca0a4c15a432c98668a7f5d94c730ae0067c199057baff0bba16f23101b3a02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 464f82962b58515d06a03ce7519f5a7e0cbdd437fd08734e636106478bd9a052 0.600000000000 1432599 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": 972690, "vin": [ { "gen": { "height": 972680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "464f82962b58515d06a03ce7519f5a7e0cbdd437fd08734e636106478bd9a052" } } ], "extra": [ 1, 81, 28, 160, 164, 193, 90, 67, 44, 152, 102, 138, 127, 93, 148, 199, 48, 174, 0, 103, 193, 153, 5, 123, 175, 240, 187, 161, 111, 35, 16, 27, 58, 2, 17, 0, 0, 0, 1, 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