Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b271ac9285ee804e75bcf4657376e6328de7d956c102cda3dc87c9a9772e6e9

Tx prefix hash: 48f2d0c74440508093095f0dd60b00e97373d81df176d2a01e26d9d825f66632
Tx public key: 8c70376663f2a2eab9cacbd7e5fe9d6e10fe8aa19d85d3da071e332ba3a6d876
Timestamp: 1718394819 Timestamp [UCT]: 2024-06-14 19:53:39 Age [y:d:h:m:s]: 00:255:04:10:38
Block: 1044255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182302 RingCT/type: yes/0
Extra: 018c70376663f2a2eab9cacbd7e5fe9d6e10fe8aa19d85d3da071e332ba3a6d87602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cd044a0d77cbfc69fc29ec5d759e57104dfa8e546a79b0eff1cd6cf96184702 0.600000000000 1513516 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": 1044265, "vin": [ { "gen": { "height": 1044255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cd044a0d77cbfc69fc29ec5d759e57104dfa8e546a79b0eff1cd6cf96184702" } } ], "extra": [ 1, 140, 112, 55, 102, 99, 242, 162, 234, 185, 202, 203, 215, 229, 254, 157, 110, 16, 254, 138, 161, 157, 133, 211, 218, 7, 30, 51, 43, 163, 166, 216, 118, 2, 17, 0, 0, 0, 5, 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