Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 910d9cdc60eeea5f8dc69b3834bf6bb63e4aa84f6f3cb781f2ef79855b00128e

Tx prefix hash: bb7caab2eb9badfe89fc7438353138708f8f919f236e1046c3094c4dab9d394d
Tx public key: 4d3d950c8d9a4dd87e13062ba4f69b458101d216a81d09ae43c3a0e88b1f01ce
Timestamp: 1730049588 Timestamp [UCT]: 2024-10-27 17:19:48 Age [y:d:h:m:s]: 00:158:13:43:49
Block: 1140840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113122 RingCT/type: yes/0
Extra: 014d3d950c8d9a4dd87e13062ba4f69b458101d216a81d09ae43c3a0e88b1f01ce021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 98a7396cbdc9ad5406f9d8bf20cb6167b93dfd92a64a565f34d76e0b91a45ed9 0.600000000000 1624643 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": 1140850, "vin": [ { "gen": { "height": 1140840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "98a7396cbdc9ad5406f9d8bf20cb6167b93dfd92a64a565f34d76e0b91a45ed9" } } ], "extra": [ 1, 77, 61, 149, 12, 141, 154, 77, 216, 126, 19, 6, 43, 164, 246, 155, 69, 129, 1, 210, 22, 168, 29, 9, 174, 67, 195, 160, 232, 139, 31, 1, 206, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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